@eddiejennings said in Dialing Plan Logic Sanity Check:

@jaredbusch

Also NXXXXXXXXX is an invalid dial pattern for NANPA. The valid pattern is NXXNXXXXXX.

You're right. I've fixed my patterns. While the invalid pattern works, it would be best to follow the standard.

It is too loose, so it would never have stopped a real call from processing.

NXX - NPA (Area Code)
NXX - Exchange (ILEC Central Office)
XXXX - Line (Station within the Exchange)

N = 2-9
X = 0-9

So this menas that NPA and Exchange 3 digit numbers can never begin with a 0 or 1.

@scottalanmiller said in FreePBX - Thinking Through Directories:

@eddiejennings said in FreePBX - Thinking Through Directories:

@scottalanmiller said in FreePBX - Thinking Through Directories:

Quantify your concern. What exactly are you worried will happen?

For the direct-dialing concern, I'm ashamed to admit that I didn't think my concern through fully. I suppose the worst that can happen is a department would be annoyed by potential crank calling their queue directly rather than waiting through the IVR options. But then again, they can simply memorize which single digit to press, and achieve the same thing.

If someone can dial you, they can dial you. Imagine this same discussion about email. "We have to hide our email DLs and aliases, what if people EMAILED us?!?!?"

Um... yeah, that's the idea.

Point taken.

I've used the built in backup. It works great, preserving everything properly, as far as I can tell.

I just had this issue with 2 users. Both were using the Grandstream Wave app softphone. Then they tried to register using the Bria app. Worked instantly. Strange behavior

@scottalanmiller said in FreePBX System CPU load:

Wasn't exactly a huge number, could have been just about anything for a small spike a few times.

Yeah. I was concerned because I wasn't expecting load to be greater that 0.5 when supposedly the system was idle.

I did a conference call test with it last night (the PBX itself handling the conference). Audio quality was terrible for me (softphone to PBX), but all of the participants, who called in via cell phones said the quality was fine. Not sure if these events are related. Perhaps it's just me getting anxious as I'm running out of preparation tasks before attempting to port numbers and actually deploying this thing. 🙂

@black3dynamite said in Remote Administration of FreePBX:

@scottalanmiller said in Remote Administration of FreePBX:

Also gives you (if you use GIT like we do) a record of when the port was opened, why and when it was closed again.

How does that work?

You commit your change to your local file system on your workstation. Then you commit it to the GIT repo. When you do this, GIT stores your change as well as the previous state of the system and you add a comment when you commit. This gives you a chance to say "Opening port to work on PBX" or whatever. Then when you are all done, change the firewall back, commit it, comment again saying you are done and closing it and it closes itself.

Makes sense. I'll continue using the method of inbound routes.

I pulled a @jaredbusch and justed used voip.ms 😄

@eddiejennings said in FreePBX and time zones:

What does the Admin > System Admin > Time Zone setting affect? Should it affect the actual system clock of the server?

Here's my scenario:

During FreePBX Install (the OS part), do not set the time zone, which defaults to UTC. After the install, reboot, log into the FreePBX GUI. During the initial setup, you're prompted to confirm a time zone. At this time I specify EST. Reports > Asterisk Logfiles show logs in UTC (which makes sense, since from the OS perspective the time zone is UTC). Envelopes for voice mails are also in UTC.

There is a setting for this, but I cannot find it right now.

@dashrender said in Unable to originate a call with the UCP in FreePBX 14:

@jaredbusch said in Unable to originate a call with the UCP in FreePBX 14:

@dashrender said in Unable to originate a call with the UCP in FreePBX 14:

@jaredbusch said in Unable to originate a call with the UCP in FreePBX 14:

@dashrender said in Unable to originate a call with the UCP in FreePBX 14:

Interesting feature, what's it main use though?

Not tieing my to me desk to make a phone call. I wear a DECT headset pretty much all day. When I am at my desk I don't need this function, but when I am working from elsewhere around the house, I cannot originate a call without it. That or I have to walk back to my office.

Luckily FOP2 also has a call origination function.

aww, since your headset doesn't have a keypad, you need this to make calls from your headset.

Why would I want a headset to have a keypad? It is a headset.

I know your just angry because you haven't had enough coffee or nooners, whatever - it's OK.

If hangry is when being hungry makes you angry, would this be cangry or nangry?

@tm1000 said in Trying the FreePBX 13 to 14 Upgrade:

@jaredbusch said in Trying the FreePBX 13 to 14 Upgrade:

The UCP is supposed to be improved, but it looks like more work instead. Need more time with that.

@bigbear said in Trying the FreePBX 13 to 14 Upgrade:

I gave the UCP a try, there was no default layout or apps. Kind of a miss there because by comparison it is maybe its stronger using-facing benefit.

@jaredbusch said in Trying the FreePBX 13 to 14 Upgrade:

That is what I am seeing and wondering WTF.

We have plans to add customization by Administrators from within User Manager. We will also note to add default layouts in there as well.

The tutorial walks you through most of this however.

More to come in time.

Yeah, a default layout would be awesome. The tutorial is good. I went through it yesterday.

@eddiejennings said in Softphones that integrate with SalesForce:

@jaredbusch said in Softphones that integrate with SalesForce:

Now integrating the PBX with SalesForce is a great idea, and can let it do lookups for CallerID or even cause the salesforce appmto issue a pop up or some such.

As I've done some research today, I believe this is the kind of thing they want -- specifically a popup with information about an incoming call.

Definitely would seem to be a PBX feature, not a endpoint device feature. A softphone is pretty much a desk phone just inside your computer via software only. I wouldn't expect a dumb phone on my desk to have this ability, but I would expect my PBX to maybe be able to accommodate this.

The only other option would be is if SalesForce is the PBX, but then, there's still a PBX involved.

For those looking to do this upgrade, the link is no longer valid. Try this one...

https://wiki.freepbx.org/display/PPS/Upgrading+from+FreePBX+10.13.66+to+SNG7

@aaronstuder Oh yes! Rackspace was about 3-4x more than what we are paying for Vultr. Not to mention much more flexibility, and performance (SSD).

@aaronstuder said in First Look at FreePBX 14:

@dashrender said in First Look at FreePBX 14:

I'm installing this for the first time on Vultr.. damn, that initial install took 20+ mins, just like JB.

Adding more resources doesn't seems to help. I did it with 2 Cores, and 2GB of RAM took the same amount of time.....

Not too many things that it is doing that are likely multithreaded. Mostly just transferring files.

@JaredBusch said in FreePBX 14 Release Candidate is out:

@tm1000 said in FreePBX 14 Release Candidate is out:

@JaredBusch that is correct

I am interested in Zulu but never set it up because a 2 users license for only a year is useless. Or does that auto renew so I always have 2 users for free? If that is the case I will set it up on my company PBX for myself and another user.

None of my clients have had an interest sadly.

Same here, time out free licenses I generally avoid.